handle unique constraints in changeColumn() for postgres #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any chance you'd be willing to add a test for that so it doesn't slip through the cracks again in the future? If not, I can write one, but I might not get to it right away. |
|
I can probably figure out how to do that. I'll try to get to it today. |
kunklejr
added a commit
that referenced
this pull request
Sep 14, 2012
handle unique constraints in changeColumn() for postgres
|
Fix is in version 0.2.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There doesn't seem to be support for unique constraints passed to the changeColumn() function for the Postgres backend; they just get ignored. I added support for it. Please pull this change into your repo.